Oklahoma NG911 Toolkit | Prep | [Enhancement] | Validation | MSAG | Comparison | Submission
Supplementary Documentation | Examples | Topology Rules | Change Log | Error Glossary
January 09, 2025
These tools automate various tasks involved with data creation and/or modifications.
Calculate/Convert/Fix
PreMod, PreDir, PreType, PreTypeSep, Street, StreetType, SufDir, and SufMod.Street, PreTyp, StreetType, PreDir and SufDir.LgcyStreet, LgcyPreTyp, LgcyType, LgcyPreDir and LgcySufDir.LEFT ('L') and RIGHT ('R')FullName and LgcyFulStFullName and LgcyFulSt fielda of the Address Point Standard feature class and/or the Road Centerline Standard feature class. For the FullName fields, the street fields are used with next-gen fields, and the legacy fields are replaced with the Legacy version of the fields for the LgcyFulSt field.FullAddr and LgcyFulAddFullAddr fand LgcyFulAdd fielda of the Address Point Standard feature class and/or the Road Centerline Standard feature class. For the FullAddr fields, the AddNumPre, AddNumber, AddNumSuf, plus the street fields are used, and the [legacy direction fields] and [legacy type fields] are preplaced with the Legacy version of the fields for the LgcyFulAdd field.Parity_L and Parity_RParity_side fields of a road centerline feature class. The fields used for the calculation are: Add_side_From and Add_side_To. The tool will used the first and last digit on both sides to determine whether the number is EVEN, ODD, BOTH, or ZERO.N.RCLMatch and RCLSideRCLMatch field. First, dataframes are created for the Address Point and Road Centerline featuer classes. Next, the street fields concatenated strings for each feature class. Then, the Road Centerline dataframe is joined to the Address Point dataframe using the street fields concatenated string. Non-matched address objects are then removed from the joined dataframe. Next, the AddNumber field value is then compare to the range of Add_side_From value to Add_side_To value with the Partiy_side used to determine the step number; this will determine the side of the road (RCLSide). Non-matches are then removed from the joined dataframe. The PreNum value is then compare the both Add_side_Pre value, and the MSAGComm field value is compared to the MSAGComm_side value. Once these comparisons are complete, the possible matches are returned. If only one match is returned, the NGUID_RDCL value is returned as RCLMatch. Values that results with ties start with the string TIES with the NGUID_RDCL values returned as a pipe-separated local:agency string. RCLSide is set to NO MATCH The rest of the non-matched values are populated as NO MATCH.MSAGCommMSAGComm field for Address Point feature class and MSAGComm_side fields for Road Centerline feature class.For issues or questions, please contact through email Riley Baird at rbaird@odot.org or Emma Baker at ebaker@odot.org with the Oklahoma Transportation Cabinet, and please include in the email which script you were running, any error messages, and a zipped copy of your geodatabase. Change the file extension from zip to piz so it gets through the email server. If there are further data transfer issues, contact Emma or Riley to make alternative data transfer arrangements.
The Oklahoma NG9-1-1 GIS Toolbox is provided by the Oklahoma Geographic Information (GI) Council, Oklahoma 9-1-1 Management Authority, Oklahoma Department of Transportation (ODOT), Oklahoma Office of Geographic Information (OGI) , and associated contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the Oklahoma GI Council, Oklahoma 9-1-1 Management Authority, ODOT, OGI, or associated contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.